4.2.1.1. ErrorCodeType
The following table defines the error codes that may be returned as an element of ErrorCodeType
.
ErrorCodeType
definitionsField | Type | Description |
---|---|---|
|
| Attempted to carry out a forbidden operation. |
|
| |
|
| The supplied |
|
| The supplied |
|
| The supplied entity is not calendar data. |
|
| The supplied entity does not represent valid calendar data. |
|
| The supplied entity does not represent valid calendar data. |
|
| Indicates that the calendar collection does not accept components of the type the client is attempting to store. The accepted component types can be determined by examining the calendar collection properties. |
|
| Error indicating at least one of two conditions:
|
|
| Error indicating that the total size of the event or task is too large. The maximum size is set by the target system and can be determined from the properties. |
|
| Error indicating that the start or end of an event or task is too far into the past. The minimum date is set by the target system and can be determined from the properties. |
|
| Error indicating that the start or end of an event or task is too far into the future. The maximum date is set by the target system and can be determined from the properties. |
|
| Error indicating that a recurring event has too many instances. The maximum number is set by the target system and can be determined from the properties. |
|
| Error indicating that a scheduling message has too many attendees. The maximum number is set by the target system and can be determined from the properties. |
|
| Indicates that a |
|
| An operation was attempted which required a change token but none was supplied. Note that it appears that the marshalling or demarshalling should handle this as the token is required. It doesn’t. |
|
| An update operation was attempted with a change token value which does not match that held by the service. The client must refetch the entity to refresh its cached value and token. Note that matching of tokens is a server responsibility. The token is opaque to the client but probably structured to the server. Certain non-conflicting updates may be allowed even if the token has changed. |
|
| |
|
| An attempt was made to store an entity which would result in more than one entity having equal |